Skip to content
This repository was archived by the owner on Oct 2, 2025. It is now read-only.

add status link to footer #17

Merged
narthur merged 1 commit into from
Sep 4, 2025
Merged

add status link to footer #17

narthur merged 1 commit into from
Sep 4, 2025

Conversation

@narthur
Copy link
Collaborator

@narthur narthur commented Sep 4, 2025 •
edited by coderabbitai bot
Loading

Summary by CodeRabbit

  • New Features
    • Added a “Status” link to the footer’s Product section, providing quick access to the live service status and incident history.
    • The link appears after “Documentation” and is available across the app for easy visibility.
    • Improves transparency and helps users quickly verify service health during incidents.
    • Purely presentational change with no impact on app behavior, performance, or user settings.

Copilot AI review requested due to automatic review settings September 4, 2025 21:08
@narthur narthur temporarily deployed to uptime-link - tr.com PR #17 September 4, 2025 21:08 — with Render Destroyed
Copilot AI reviewed Sep 4, 2025
View reviewed changes
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a status page link to the footer of the website, providing users with easy access to service status information.

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@coderabbitai
Copy link

coderabbitai bot commented Sep 4, 2025 •
edited
Loading

Walkthrough

A single Svelte component was updated to add a new “Status” link in the footer’s Product section, placed after the “Documentation” link. No logic or state changes were introduced.

Changes

Cohort / File(s) Summary
Footer UI update
src/components/Footer.svelte		 Inserted a new anchor list item linking to https://status.taskratchet.com/ in the Product section after Documentation; markup-only change, no state or logic affected.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers, links aligned,
A “Status” hop in footer’s line.
No scripts to chase, no states to tend—
Just tidy trails that neatly end.
Beneath the moon, I stamp and cheer:
The Product burrow’s clearer here! 🐇✨

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch uptime-link

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot]
coderabbitai bot reviewed Sep 4, 2025
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
src/components/Footer.svelte (2)

10-10: Confirm desired behavior for external link

If you want the status page to open in a new tab, add target and rel for safety.

-          <li><a href="https://status.taskratchet.com/">Status</a></li>
+          <li><a href="https://status.taskratchet.com/" target="_blank" rel="noopener noreferrer">Status</a></li>

79-90: Deduplicate anchor styles to avoid drift

.footer-section a is defined twice (once alone and once grouped with .footer-bottom a). Keep only the grouped rule.

-  .footer-section a {
-    color: var(--text-secondary);
-    text-decoration: none;
-    transition: color 0.2s ease;
-  }
-
-  .footer-section a,
-  .footer-bottom a {
+  .footer-section a,
+  .footer-bottom a {
     color: var(--text-secondary);
     text-decoration: none;
     transition: color 0.2s ease;
   }
📜 Review details

Configuration used: Repository: TaskRatchet/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 2ea7d81 and bc70ea7.

📒 Files selected for processing (1)
  • src/components/Footer.svelte (1 hunks)
🔇 Additional comments (1)
src/components/Footer.svelte (1)

10-10: Status link added — LGTM

Placement and URL look good.

@narthur narthur merged commit cfc292c into master Sep 4, 2025
5 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

Copilot code review Copilot Copilot left review comments

+1 more reviewer

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@narthur